Hyperledger fabric version

The intention of Hyperledger Fabric is to become a foundation for developing

applications with a modular architecture allowing components, such as

consensus and membership services, to be plug-and-play. A broad range of

industry use cases is satisfied by its modular and versatile design. While

preserving privacy, it offers a unique approach to the consensus that enables

performance at scale. One of the many compelling Fabric features is the

enablement of a network of networks. Members of a network work together,

but because businesses need some of their data to remain private, they often

maintain separate relationships within their networks. The “channels” feature

makes this possible in Hyperledger Fabric. If you need total transaction

isolation and the “private data” feature if you would like to keep data private

while sharing hashes as transaction evidence on the ledger.

Fabric offers a scalable and secure platform that supports private transactions

and confidential contracts rather than j ust being an open, permissionless

system. This architecture allows for solutions developed with Fabric to be

adapted for any industry, thus ushering in a new era of trust, transparency, and

accountability for businesses.

The first Hyperledger Fabric maj or release since v1.0, Fabric v2.0 delivers

important new features and changes for users and operations alike, including

support for new application and privacy patterns, enhanced governance around

smart contracts, and new options for operating nodes.

Each v2.x minor release builds on the v2.0 release with minor features,

improvements, and bug fixes. v2.2 is the first long-term support (LTS)

release of Fabric v2.x. Fixes will be provided on v2.2.x release stream until

after the next LTS release is announced.

The following are the highlights of the Fabric v2.0 release:

1. Smart contracts decentralized governance

Smart contracts decentralized governance is introduced in Fabric v2.0, with a

new process for installing a chaincode on your peers and starting it on a

channel. The new Fabric chaincode life cycle allows multiple organizations to

come to an agreement on the parameters of a chaincode, such as the chaincode

endorsement policy before it can be used to interact with the ledger.

1. For collaboration and consensus, new chaincode application patterns